Resistance to leave AF2 / Backward Mode
Original Post
I'm having some trouble with the switch to AF4. With AF2, I can be very specific about things that I have to do at work, knowing that I'll reach them very fast. For example, I can put:
Work on bug #1234
Continue development of report
Pay bill
Work on bug #1240
Fix data errors
Call mom
et c...
After fixing a bug, I immediately want to reach the next one. If I find some non-work task in the middle that I can allow myself to work on (like “Pay bill”), I do it.
With AF1/4 I have to loop through pages/backlog. I know I won't be able to work on most of these tasks now. As I used to do with AF1, I'd have to concentrate all the bugs and work related stuff in a single task, “Work on Billing System”, and keep the detail on a separate system. But this way, I can't apply the benefits of AF to my specific work tasks.
I think that AF1/4 suits people who have a lot of discretionary time.
For me, having a couple of bosses, and dozens of anxious users, AF2 seems like better choice. I can't stop working in the middle of the day to water the plants :-)
RAF with its two modes had the potential to be the solution I needed, but I could never reach Forward Mode. But this, in some way, reflects my reality.
I know I can keep using AF2, but knowing that Mark has already replaced it, makes me feel like using an old version of a program (something I never liked).
I will try AF4 anyway, I might be surprised, but I suspect that it won't be as effective for me.
Work on bug #1234
Continue development of report
Pay bill
Work on bug #1240
Fix data errors
Call mom
et c...
After fixing a bug, I immediately want to reach the next one. If I find some non-work task in the middle that I can allow myself to work on (like “Pay bill”), I do it.
With AF1/4 I have to loop through pages/backlog. I know I won't be able to work on most of these tasks now. As I used to do with AF1, I'd have to concentrate all the bugs and work related stuff in a single task, “Work on Billing System”, and keep the detail on a separate system. But this way, I can't apply the benefits of AF to my specific work tasks.
I think that AF1/4 suits people who have a lot of discretionary time.
For me, having a couple of bosses, and dozens of anxious users, AF2 seems like better choice. I can't stop working in the middle of the day to water the plants :-)
RAF with its two modes had the potential to be the solution I needed, but I could never reach Forward Mode. But this, in some way, reflects my reality.
I know I can keep using AF2, but knowing that Mark has already replaced it, makes me feel like using an old version of a program (something I never liked).
I will try AF4 anyway, I might be surprised, but I suspect that it won't be as effective for me.
Reply by Andreas Hofmann
<< I know I can keep using AF2, but knowing that Mark has already replaced it, makes me feel like using an old version of a program (something I never liked). >>
I think that's the wrong way to think about it. If AF2 works great for you, you don't need a "better" version. There are many people who had issues with AF2, which where addressed with RAF. And the issues people had with RAF where addressed with AF4. ;-)
So unless you have issues with your current setup, don't worry about being "current".
Old IT wisdom: Never change a running system.
For example, I never upgraded from XP to Vista. Vista was "newer", but it didn't solve any problem I had with XP, so keeping XP was the logical choice.
I think that's the wrong way to think about it. If AF2 works great for you, you don't need a "better" version. There are many people who had issues with AF2, which where addressed with RAF. And the issues people had with RAF where addressed with AF4. ;-)
So unless you have issues with your current setup, don't worry about being "current".
Old IT wisdom: Never change a running system.
For example, I never upgraded from XP to Vista. Vista was "newer", but it didn't solve any problem I had with XP, so keeping XP was the logical choice.
Reply by Andreas Hofmann
Of course, nothing wrong with experimentation, i.e. dual-booting linux beside windows or experimenting with AF4 to see how you like it. But don't feel like you *have* to do it. :-)
Reply by Walter
AF-XP ?
I know you're right, Andreas, when talking about software.
But I feel that new AF versions are created to deal with flaws from the previous ones.
Maybe AF should consist on several methods, tailored for different kind of users.
This could open the possibility for Mark to produce a book.
Maybe something like “Choose Your Own Adventure”. In the end, you would have your own personal AF system. :-)
I know you're right, Andreas, when talking about software.
But I feel that new AF versions are created to deal with flaws from the previous ones.
Maybe AF should consist on several methods, tailored for different kind of users.
This could open the possibility for Mark to produce a book.
Maybe something like “Choose Your Own Adventure”. In the end, you would have your own personal AF system. :-)
Reply by Andreas Hofmann
<< Maybe AF should consist on several methods, tailored for different kind of users. >>
That's the way I see the existing systems. ;-)
That's the reason we I won't throw away my AutofocusCC which implements AF1 or my AutofocusAHK which implements RAF. I think they both still have their merits for different kinds of users. In the next days, I'll modify AutofocusAHK to let the user choose between AF1, AF2, (R)AF3 and AF4. So everyone can use it the way he thinks is best for him.
That's the way I see the existing systems. ;-)
That's the reason we I won't throw away my AutofocusCC which implements AF1 or my AutofocusAHK which implements RAF. I think they both still have their merits for different kinds of users. In the next days, I'll modify AutofocusAHK to let the user choose between AF1, AF2, (R)AF3 and AF4. So everyone can use it the way he thinks is best for him.
Reply by Andreas Hofmann
<>
I think the comparison isn't that far fetched. If I would change the OS of my computer, I'd need time to set the new system up, perhaps I couldn't use the same programs as before and had to learn new ways of using the computer. If you change your time management system, you must set the new system up, which takes time. You must get accustomed to the new way things are done in the new system, your experience with the old system may be useless or even hinder you.
<>
They are. My point is: do those flaws affect you? If you have the feeling something is amiss in your system, then maybe a different version solves that problem. But if you're doing fine with AF2, you're okay.
I think the comparison isn't that far fetched. If I would change the OS of my computer, I'd need time to set the new system up, perhaps I couldn't use the same programs as before and had to learn new ways of using the computer. If you change your time management system, you must set the new system up, which takes time. You must get accustomed to the new way things are done in the new system, your experience with the old system may be useless or even hinder you.
<
They are. My point is: do those flaws affect you? If you have the feeling something is amiss in your system, then maybe a different version solves that problem. But if you're doing fine with AF2, you're okay.
Reply by Rob...
Walter,
Have you considered two AF4 lists? One for home and one for work.
Regards,
Rob...
Have you considered two AF4 lists? One for home and one for work.
Regards,
Rob...
Reply by Walter
>> My point is: do those flaws affect you?
Yes and no: Working on the latest tasks somehow calms my anxiety and user's, but at the same time, I'm neglecting the older stuff. This is one of the things people complained about AF2.
RAF's intentions fitted me perfectly. A system that lets me to work both ways. But it wasn't strict enough when it was time to make the switch to Forward Mode.
I could use an improved AF2/RAF. In fact, I "patched" AF2 very effectively (with a system that forces me to either promote older tasks to the end, or kill them).
But I'd prefer to be in sync with Mark's developments (he's the expert). AF4 removed backward mode, and I don't see how it deals with urgent items better than AF1 (wasn't enough for me, I had to use additional tools).
But as usual with AF, I should try it before reaching conclusions. Even if I resist the idea.
Yes and no: Working on the latest tasks somehow calms my anxiety and user's, but at the same time, I'm neglecting the older stuff. This is one of the things people complained about AF2.
RAF's intentions fitted me perfectly. A system that lets me to work both ways. But it wasn't strict enough when it was time to make the switch to Forward Mode.
I could use an improved AF2/RAF. In fact, I "patched" AF2 very effectively (with a system that forces me to either promote older tasks to the end, or kill them).
But I'd prefer to be in sync with Mark's developments (he's the expert). AF4 removed backward mode, and I don't see how it deals with urgent items better than AF1 (wasn't enough for me, I had to use additional tools).
But as usual with AF, I should try it before reaching conclusions. Even if I resist the idea.
Reply by Walter
Rob,
"Have you considered two AF4 lists? One for home and one for work."
That's what I used to do with AF1, and it certainly worked. But AF2 allowed me to use a single list, and its hard to go back.
Not only because of the overhead. I very seldom opened the Home list when I was using AF1.
"Have you considered two AF4 lists? One for home and one for work."
That's what I used to do with AF1, and it certainly worked. But AF2 allowed me to use a single list, and its hard to go back.
Not only because of the overhead. I very seldom opened the Home list when I was using AF1.
Reply by Nicole
The way AF4 deals better with urgent stuff than AF1 is that in AF1, you would have to do something on EVERY page to prevent the entire page from being dismissed, before you could reach any urgent items near the end of the list. With AF4, you only need to action ONE item from the closed list to prevent everything being dismissed, before moving on to the open list where your latest urgent items are. Reading through the entire closed and open lists before reaching any urgent items near the end of the list helps me decide if there's really nothing hidden in either list that has become more urgent than the newer urgent tasks at the end.
I could imagine that if your work requires you to react to emergencies right away (like in NOW instead of within a few minutes) AF4 wouldn't work as well as AF2 or RAF. For my work, I've noticed that AF2/RAF allows me to react to semi-emergencies much too quick, at the expense of more important stuff. So for me, I think AF4 is going to work very well. The only resistance I have in leaving AF2/RAF is that it just feels good to respond to emergencies, even when at the expense of more important (and often a bit more boring) older tasks.
Oh, and the other concern I have is the same as yours, Walter, dealing with Home and Work stuff. I might go back to the dual mode list (work stuff from the top, home stuff from the bottom) that I used in AF1, but I'll start with one integrated list first, to see how that works.
I could imagine that if your work requires you to react to emergencies right away (like in NOW instead of within a few minutes) AF4 wouldn't work as well as AF2 or RAF. For my work, I've noticed that AF2/RAF allows me to react to semi-emergencies much too quick, at the expense of more important stuff. So for me, I think AF4 is going to work very well. The only resistance I have in leaving AF2/RAF is that it just feels good to respond to emergencies, even when at the expense of more important (and often a bit more boring) older tasks.
Oh, and the other concern I have is the same as yours, Walter, dealing with Home and Work stuff. I might go back to the dual mode list (work stuff from the top, home stuff from the bottom) that I used in AF1, but I'll start with one integrated list first, to see how that works.
Reply by Walter
Interesting points, Nicole.
I still see a problem with re-reading the whole backlog for each task that I finish in the active list.
I could use "common sense" and just skip it, but then, I would be cheating the system as it is.
I still see a problem with re-reading the whole backlog for each task that I finish in the active list.
I could use "common sense" and just skip it, but then, I would be cheating the system as it is.
Reply by Nicole
Yep, I feel the same about re-reading the whole backlog. So far I've managed not to cheat too much, but it feels like a chore, probably also because my list is rather long (>200 items). I was hoping AF4 would speed up the dismissal process to reduce that, and I think it will, but not for a few days yet..
Reply by Andreas
Walter:
<< I still see a problem with re-reading the whole backlog for each task that I finish in the active list. >>
Why must you re-read the backlog for *each* task on the active list? After leaving the backlog, you could do every single task on the active list without ever going back to the backlog.
<< I still see a problem with re-reading the whole backlog for each task that I finish in the active list. >>
Why must you re-read the backlog for *each* task on the active list? After leaving the backlog, you could do every single task on the active list without ever going back to the backlog.
Reply by Mike
Nichole, Walter,
1) As Andreas said, you might have misunderstood the instruction. Step through his PDF and watch the system unfold as Mark did it, but in warp speed ;-)
2) You DO have to work through the entire backlog, perhaps several times, for each PASS through the open list. BUT that is a GOOD thing. It is what forces you to reach the point of dismissal as quickly as possible. It is what makes the system fast.
3) You can't "cheat" a TM system. It is there to serve your needs. If you need to change the way you do things ... change them.
4) Yes, Mark is the expert, but he is mostly the expert on what works for him. Remember, he is testing and developing based on how he does things. If your environment is different, what works for you might be different. I'm sure the very last thing Mark wants is to be seen as a Guru. (Except, perhaps, if it advances his agenda to take over the world! ;-)
1) As Andreas said, you might have misunderstood the instruction. Step through his PDF and watch the system unfold as Mark did it, but in warp speed ;-)
2) You DO have to work through the entire backlog, perhaps several times, for each PASS through the open list. BUT that is a GOOD thing. It is what forces you to reach the point of dismissal as quickly as possible. It is what makes the system fast.
3) You can't "cheat" a TM system. It is there to serve your needs. If you need to change the way you do things ... change them.
4) Yes, Mark is the expert, but he is mostly the expert on what works for him. Remember, he is testing and developing based on how he does things. If your environment is different, what works for you might be different. I'm sure the very last thing Mark wants is to be seen as a Guru. (Except, perhaps, if it advances his agenda to take over the world! ;-)
Reply by Seraphim
I guess I missed the instruction that you're supposed to read through the entire backlog, before taking any action on it.
I don't see that in Mark's "preliminary instructions" -- he just says
3) You start with the Backlog. Look through the tasks in the Backlog in order and work on any tasks which feel ready to be done. Delete each task when you feel you have worked on it for long enough, and re-enter it at the end of the Active List if you need to do more work on it.
http://www.markforster.net/blog/2009/9/5/preliminary-instructions-for-autofocus-v-4.html
And I also didn't see it in the demo.
If I had to read through my backlog every single time I started afresh on the Closed List, this certainly wouldn't work for me.
But as the rules are written, it's working GREAT!
I don't see that in Mark's "preliminary instructions" -- he just says
3) You start with the Backlog. Look through the tasks in the Backlog in order and work on any tasks which feel ready to be done. Delete each task when you feel you have worked on it for long enough, and re-enter it at the end of the Active List if you need to do more work on it.
http://www.markforster.net/blog/2009/9/5/preliminary-instructions-for-autofocus-v-4.html
And I also didn't see it in the demo.
If I had to read through my backlog every single time I started afresh on the Closed List, this certainly wouldn't work for me.
But as the rules are written, it's working GREAT!
Reply by Walter
Andreas,
>> Why must you re-read the backlog for *each* task on the active list? After leaving the backlog, you could do every single >> task on the active list without ever going back to the backlog.
You are right, my mistake. I have a full single pass through the active list. Maybe I could work it in reverse mode? Hm...
Anyway, I feel that the backlog receives more importance than the active list (multiple looping).
>> Why must you re-read the backlog for *each* task on the active list? After leaving the backlog, you could do every single >> task on the active list without ever going back to the backlog.
You are right, my mistake. I have a full single pass through the active list. Maybe I could work it in reverse mode? Hm...
Anyway, I feel that the backlog receives more importance than the active list (multiple looping).
Reply by AndreasE
I'm pretty sure it won't become forbidden to continue using AF1 - 3. We are not talking about lightbulbs here... :-(
Reply by Walter
I know, I know... I'm assume that he replaced it for some reason, though...
AF2, as much as I like it, has its flaws.
AF2, as much as I like it, has its flaws.
Reply by Walter
Sorry about the typos, damn.
Reply by Mark Forster
Mike:
<< I'm sure the very last thing Mark wants is to be seen as a Guru. (Except, perhaps, if it advances his agenda to take over the world! ;-) >>
<< I'm sure the very last thing Mark wants is to be seen as a Guru. (Except, perhaps, if it advances his agenda to take over the world! ;-) >>
Reply by Mark Forster
Walter:
<< I feel that the backlog receives more importance than the active list (multiple looping) >>
Don't forget that the proportion of tasks in the Backlog and the Active List varies from :
All tasks in backlog, none in active list
to
Hardly any tasks in backlog, nearly all in active list.
As the Backlog is squeezed smaller, so the Active List get larger.
<< I feel that the backlog receives more importance than the active list (multiple looping) >>
Don't forget that the proportion of tasks in the Backlog and the Active List varies from :
All tasks in backlog, none in active list
to
Hardly any tasks in backlog, nearly all in active list.
As the Backlog is squeezed smaller, so the Active List get larger.
Reply by Mark Forster
Walter:
To answer your original query, in the circumstances you describe I would use a subsidiary list for the bug fixes. And if I had an unrelated task I wanted to do in the middle of bug fixing, then I would put it on the bug-fixing list.
To answer your original query, in the circumstances you describe I would use a subsidiary list for the bug fixes. And if I had an unrelated task I wanted to do in the middle of bug fixing, then I would put it on the bug-fixing list.
Reply by Mike
Mark,
Yes, the demo showed the change in proportion very well. After a full day of processing my numbers went from: (open tasks on Closed list / open tasks on Open list)
29/73 Start Yesteday
21/99 End Yesterday
20/118 Now
My closed list is moving much slower than it would expect it to normally. When I transferred my tasks from my other book for this experiment, I did not make them all "backlog". I probably should have done that. Since I drew the line more "logically" (IOW, what I felt was really the backlog) the few tasks on my closed list are really ones that were already about to be dismissed or needed to wait for the next business day (after a long holiday weekend). I'll most likely dismiss sometime today then have about 130 or so tasks in backlog.
I'll bet with that much longer closed list, I'll have an entirely different experience than I am having now. I can also see where the single pass of the open list will make much more sense as the list will only be 6 or 7 items to start.
Yes, the demo showed the change in proportion very well. After a full day of processing my numbers went from: (open tasks on Closed list / open tasks on Open list)
29/73 Start Yesteday
21/99 End Yesterday
20/118 Now
My closed list is moving much slower than it would expect it to normally. When I transferred my tasks from my other book for this experiment, I did not make them all "backlog". I probably should have done that. Since I drew the line more "logically" (IOW, what I felt was really the backlog) the few tasks on my closed list are really ones that were already about to be dismissed or needed to wait for the next business day (after a long holiday weekend). I'll most likely dismiss sometime today then have about 130 or so tasks in backlog.
I'll bet with that much longer closed list, I'll have an entirely different experience than I am having now. I can also see where the single pass of the open list will make much more sense as the list will only be 6 or 7 items to start.
Reply by Mark Forster
Mike:
My own experience is that I spend about the same amount of time on the backlog each time I visit it regardless of how big it is.
I move very fast through it when it is very big and most tasks (including all the easy ones!) are in it.
When it's smaller and more difficult I move slower and proportionally more of it gets done, but the overall time spent is very approximately the same.
My own experience is that I spend about the same amount of time on the backlog each time I visit it regardless of how big it is.
I move very fast through it when it is very big and most tasks (including all the easy ones!) are in it.
When it's smaller and more difficult I move slower and proportionally more of it gets done, but the overall time spent is very approximately the same.
Reply by Walter
Mark,
"To answer your original query, in the circumstances you describe I would use a subsidiary list for the bug fixes. And if I had an unrelated task I wanted to do in the middle of bug fixing, then I would put it on the bug-fixing list."
Do you mean an Autofocus list for bugs, or a different kind of list specific to bug management (with all kind of additional data related to bugs)? I built a system for bug management, but with AF2/RAF I've been neglecting it lately.
If its the first option, I would work similarly to when I was using AF1. One list for home, one for work (including bugs and other stuff).
I very much want to stay with a single list. Maybe I'll add a single task "Work on system X" and then I'll use my project management program to get into details. It was nice having all together, though, but maybe not ideal.
Thanks for answering. I'm going to start trying AF4 now.
"To answer your original query, in the circumstances you describe I would use a subsidiary list for the bug fixes. And if I had an unrelated task I wanted to do in the middle of bug fixing, then I would put it on the bug-fixing list."
Do you mean an Autofocus list for bugs, or a different kind of list specific to bug management (with all kind of additional data related to bugs)? I built a system for bug management, but with AF2/RAF I've been neglecting it lately.
If its the first option, I would work similarly to when I was using AF1. One list for home, one for work (including bugs and other stuff).
I very much want to stay with a single list. Maybe I'll add a single task "Work on system X" and then I'll use my project management program to get into details. It was nice having all together, though, but maybe not ideal.
Thanks for answering. I'm going to start trying AF4 now.
Reply by Mark Forster
Walther:
I was thinking more in terms of a simple list like a shopping list or a packing list, in which you would do the items in whatever seemed the most logical order.
I was thinking more in terms of a simple list like a shopping list or a packing list, in which you would do the items in whatever seemed the most logical order.
Reply by Mike
Walter,
FWIW, my implemenatation is to have project and shopping lists and other things of that kind in the back of my book ... working twoard the front. Then my entry is "Work on X" where "X" is a list in the back of the book where steps are listed. While that is not exactly one "list", it does keep you in one "book".
FWIW, my implemenatation is to have project and shopping lists and other things of that kind in the back of my book ... working twoard the front. Then my entry is "Work on X" where "X" is a list in the back of the book where steps are listed. While that is not exactly one "list", it does keep you in one "book".
Reply by Walter
Hi Mike,
Realistically, the proper place to list my bugs is in my dedicated system. Actually, I update them in both places.
But it's nice having them managed by AF, using intuition/dismissal and other AF features.
But its no big (or huge) deal. I didn't start trying AF4 yet. Maybe things will get arranged by themselves once I start.
Thanks
Realistically, the proper place to list my bugs is in my dedicated system. Actually, I update them in both places.
But it's nice having them managed by AF, using intuition/dismissal and other AF features.
But its no big (or huge) deal. I didn't start trying AF4 yet. Maybe things will get arranged by themselves once I start.
Thanks